Support deployment_config/working_dir value by TimoSteuerwaldETAS · Pull Request #356 · eclipse-score/lifecycle

TimoSteuerwaldETAS · 2026-07-23T14:39:33Z

This fixes #343 .
Furthermore the config mapping tests have been fixed and are executed on the pipeline.
A feature integration test has been also added which is testing various options, not only working dir.

github-actions · 2026-07-23T14:40:27Z

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: 58b31573-34e4-443f-a7b1-b234e255ea1d
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (31 packages loaded, 10 targets configured)

Analyzing: target //:license-check (86 packages loaded, 10 targets configured)

Analyzing: target //:license-check (90 packages loaded, 10 targets configured)

Analyzing: target //:license-check (144 packages loaded, 2479 targets configured)

Analyzing: target //:license-check (161 packages loaded, 6249 targets configured)

Analyzing: target //:license-check (167 packages loaded, 6298 targets configured)

Analyzing: target //:license-check (167 packages loaded, 6298 targets configured)

Analyzing: target //:license-check (170 packages loaded, 8185 targets configured)

Analyzing: target //:license-check (170 packages loaded, 8185 targets configured)

Analyzing: target //:license-check (170 packages loaded, 8185 targets configured)

Analyzing: target //:license-check (173 packages loaded, 11401 targets configured)

Analyzing: target //:license-check (174 packages loaded, 11409 targets configured)

Analyzing: target //:license-check (174 packages loaded, 11409 targets configured)

Analyzing: target //:license-check (174 packages loaded, 11409 targets configured)

Analyzing: target //:license-check (174 packages loaded, 11409 targets configured)

Analyzing: target //:license-check (174 packages loaded, 11409 targets configured)

INFO: Analyzed target //:license-check (175 packages loaded, 11535 targets configured).
[14 / 16] [Prepa] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar
[15 / 16] Building license.check.license_check.jar (); 0s disk-cache, multiplex-worker
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 35.015s, Critical Path: 2.48s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

github-actions · 2026-07-23T14:51:13Z

The created documentation from the pull request is available at: docu-html

- add another process - parameterize sandbox_options_process.cpp

Instead of hardcoded path in python.

sandbox_options_process_b was stuck in rare cases, as it never got cpu time and ran into timeout. This was caused by the minimal priority. So priority has been added here. Furthermore process_c added to check default options.

process_c configures neither a component-level working_dir nor one in the defaults section, so the launch manager falls back to bin_dir. Pass the expected default via --working-dir so the test verifies the default working directory path, mirroring how process_a verifies an explicit one. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Before, this warning appeared: Test execution time ... outside of range for MODERATE tests. Consider setting timeout="short" or size="small".

Resp. remove outdated file names

Proxy was missing during sudo apt commands. Now config file for apt is written, which uses the content of the environment variable $http_proxy

Instead provide a way to keep environment variables needed on run time private.

To be used also to signal test_end.

Currently not passing.

This reverts commit 9e44e31.

github-project-automation Bot added this to LCM - Lifecycle & Health FT Jul 23, 2026

github-project-automation Bot moved this to Backlog in LCM - Lifecycle & Health FT Jul 23, 2026

TimoSteuerwaldETAS requested a deployment to workflow-approval July 23, 2026 14:39 — with GitHub Actions Waiting

TimoSteuerwaldETAS requested a deployment to workflow-approval July 23, 2026 16:51 — with GitHub Actions Waiting

TimoSteuerwaldETAS requested a deployment to workflow-approval July 23, 2026 17:09 — with GitHub Actions Waiting

TimoSteuerwaldETAS mentioned this pull request Jul 23, 2026

[launch_manager] Honor deployment_config.working_dir as the spawned process cwd #343

Closed

TimoSteuerwaldETAS marked this pull request as ready for review July 23, 2026 17:12

TimoSteuerwaldETAS requested a deployment to workflow-approval July 24, 2026 06:47 — with GitHub Actions Waiting